-
Notifications
You must be signed in to change notification settings - Fork 332
Neptune CVE issues fix #3133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Neptune CVE issues fix #3133
Conversation
|
⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done |
1 similar comment
|
⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done |
|
✅ I finished the code review, and didn't find any security or code quality issues. |
1 similar comment
|
✅ I finished the code review, and didn't find any security or code quality issues. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3133 +/- ##
============================================
+ Coverage 63.67% 68.32% +4.64%
- Complexity 4344 5007 +663
============================================
Files 621 636 +15
Lines 23286 24162 +876
Branches 2859 2998 +139
============================================
+ Hits 14827 16508 +1681
+ Misses 7070 6218 -852
- Partials 1389 1436 +47 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Head branch was pushed to by a user without write access
7698374 to
5b55992
Compare
Issue #, if available:
Description of changes:
Fixed CVE issues (CVE-2025-48734, CVE-2025-48924) for Neptune connector.
Please find attached below test documents.
Neptune CVE Issues Fix.docx
NEPTUNE_FUNCTIONAL_TEST_2025-12-01.xlsx
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.